Autogenerated HTML docs for v1.8.3-101-g727a4
diff --git a/technical/api-parse-options.html b/technical/api-parse-options.html index c2c074e..b67d5a2 100644 --- a/technical/api-parse-options.html +++ b/technical/api-parse-options.html
@@ -798,6 +798,8 @@ Boolean long options can be <em>negated</em> (or <em>unset</em>) by prepending <code>no-</code>, e.g. <code>--no-abbrev</code> instead of <code>--abbrev</code>. Conversely, options that begin with <code>no-</code> can be <em>negated</em> by removing it. + Other long options can be unset (e.g., set string to NULL, set + integer to 0) by prepending <code>no-</code>. </p> </li> <li> @@ -1061,6 +1063,15 @@ </p> </dd> <dt class="hdlist1"> +<code>OPT_EXPIRY_DATE(short, long, &int_var, description)</code> +</dt> +<dd> +<p> + Introduce an option with expiry date argument, see <code>parse_expiry_date()</code>. + The timestamp is put into <code>int_var</code>. +</p> +</dd> +<dt class="hdlist1"> <code>OPT_CALLBACK(short, long, &var, arg_str, description, func_ptr)</code> </dt> <dd> @@ -1231,7 +1242,7 @@ <div id="footnotes"><hr /></div> <div id="footer"> <div id="footer-text"> -Last updated 2013-02-05 21:07:26 PST +Last updated 2013-05-29 16:56:14 PDT </div> </div> </body>
diff --git a/technical/api-parse-options.txt b/technical/api-parse-options.txt index 32ddc1c..1317db4 100644 --- a/technical/api-parse-options.txt +++ b/technical/api-parse-options.txt
@@ -41,6 +41,8 @@ * Boolean long options can be 'negated' (or 'unset') by prepending `no-`, e.g. `--no-abbrev` instead of `--abbrev`. Conversely, options that begin with `no-` can be 'negated' by removing it. + Other long options can be unset (e.g., set string to NULL, set + integer to 0) by prepending `no-`. * Options and non-option arguments can clearly be separated using the `--` option, e.g. `-a -b --option -- --this-is-a-file` indicates that @@ -174,6 +176,10 @@ Introduce an option with date argument, see `approxidate()`. The timestamp is put into `int_var`. +`OPT_EXPIRY_DATE(short, long, &int_var, description)`:: + Introduce an option with expiry date argument, see `parse_expiry_date()`. + The timestamp is put into `int_var`. + `OPT_CALLBACK(short, long, &var, arg_str, description, func_ptr)`:: Introduce an option with argument. The argument will be fed into the function given by `func_ptr`
diff --git a/technical/pack-protocol.html b/technical/pack-protocol.html index aabb2c3..d33806a 100644 --- a/technical/pack-protocol.html +++ b/technical/pack-protocol.html
@@ -974,8 +974,7 @@ <div class="paragraph"><p>The client MUST write all obj-ids which it only has shallow copies of (meaning that it does not have the parents of a commit) as <em>shallow</em> lines so that the server is aware of the limitations of -the client’s history. Clients MUST NOT mention an obj-id which -it does not know exists on the server.</p></div> +the client’s history.</p></div> <div class="paragraph"><p>The client now sends the maximum commit history depth it wants for this transaction, which is the number of commits it wants from the tip of the history, if any, as a <em>deepen</em> line. A depth of 0 is the @@ -1298,7 +1297,7 @@ <div id="footnotes"><hr /></div> <div id="footer"> <div id="footer-text"> -Last updated 2012-11-20 13:06:02 PST +Last updated 2013-05-29 16:56:14 PDT </div> </div> </body>
diff --git a/technical/pack-protocol.txt b/technical/pack-protocol.txt index f1a51ed..b898e97 100644 --- a/technical/pack-protocol.txt +++ b/technical/pack-protocol.txt
@@ -228,8 +228,7 @@ The client MUST write all obj-ids which it only has shallow copies of (meaning that it does not have the parents of a commit) as 'shallow' lines so that the server is aware of the limitations of -the client's history. Clients MUST NOT mention an obj-id which -it does not know exists on the server. +the client's history. The client now sends the maximum commit history depth it wants for this transaction, which is the number of commits it wants from the
